Dynamic allocation of transmission slots based on UE information

ABSTRACT

A radio access network (RAN) configured to provide allocations of transmission slots to user equipment (UEs) is described herein. The RAN may receive indicia about RAN conditions or about UEs in a vicinity of the RAN. Responsive to receiving the indicia, the RAN may determine, based at least in part on the indicia, a first allocation of uplink and downlink transmission slots to a first UE and a second allocation of uplink and downlink transmission slots to a second UE. The first allocation may differ from the second allocation. The RAN may then provide the first allocation to the first UE and the second allocation to the second UE.

RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 16/696,509, filed on Nov. 26, 2019, titled,“DYNAMIC ALLOCATION OF TRANSMISSION SLOTS BASED ON UE INFORMATION,” theentirety of which is incorporated herein by reference.

BACKGROUND

Allocation of time slots for uplink transmission and downlinktransmission (referred to herein as “transmission slots”) typicallyfollows standardized ratios of downlink to uplink. For example, threedownlink slots may be allocated for every one uplink slot. Whilestandards allow for varying allocation at radio access networks (RANs),in practice allocation is the same at each RAN. This is to ensure thatdifferent carriers who are sharing a spectrum band do not utilize thespectrum in a conflicting manner.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items or features.

FIG. 1 illustrates an example overview of a RAN configured to provideallocations of transmission slots to user equipment (UEs) based at leastin part on RAN conditions and/or indicia about the UEs.

FIG. 2 illustrates a flow chart of an example process for receivingindicia from UEs, determining allocations of transmission slots to UEs,and providing those allocations.

FIG. 3 illustrates a flow chart of an example process for providingindicia to a RAN and receiving in return an allocation of transmissionslots.

FIG. 4 illustrates an example architecture of a computing device of aRAN configured to receive indicia from UEs and to provide, in return, anallocation of transmission slots to the UEs.

FIG. 5 illustrates an example architecture of a computing device of a UEconfigured to provide indicia to a RAN and to receive, in return, anallocation of transmission slots.

DETAILED DESCRIPTION

A RAN configured to provide allocations of transmission slots to UEs isdescribed herein. The RAN may receive from UEs indicia about RANconditions or about UEs in a vicinity of the RAN. Responsive toreceiving the indicia, the RAN may determine, based at least in part onthe indicia, a first allocation of uplink and downlink transmissionslots to a first UE and a second allocation of uplink and downlinktransmission slots to a second UE. The first allocation may differ fromthe second allocation. The RAN may then provide the first allocation tothe first UE and the second allocation to the second UE.

In various implementations, a UE as described above may be configured tosend a first request for a first allocation of uplink transmission slotsand downlink transmission slots from the RAN. The request may includeindicia about RAN conditions or about the UE. The UE may then receive,in response, the first allocation of uplink transmission slots anddownlink transmission slots from the RAN. At a subsequent time, the UEmay change its location or change the application that is currentlyactive. The UE may determine the occurrence of such a change and, inresponse, request from the RAN a second allocation of uplinktransmission slots and downlink transmission slots. The RAN may thenprovide the allocation. In some implementations, the first allocationmay differ from the second allocation.

Overview

FIG. 1 illustrates an example overview of a RAN configured to provideallocations of transmission slots to UEs based at least in part on RANconditions and/or indicia about the UEs. As illustrated in FIG. 1 , aRAN 102 having a cell 104 may be connected to multiple UEs 106 locatedwithin the cell 104. A first UE 106 a may provide indicia 108 to the RAN102, and a second UE 106 b may provide indicia 112 to the RAN 102. Whenreferring to either of UEs 106 a or 106 b, or to an instance of otherUEs 106, reference is made herein to a “UE 106.” In response toreceiving indicia 108 and 112, the RAN 102 may provide an allocation 110of transmission slots to the first UE 106 a and an allocation 114 oftransmission slots to the second UE 106 b. Before providing theallocations 110 and 114, the RAN 102 may communicate with a core networkservice 116 which negotiates 118 with another telecommunication network120 to coordinate allocation of transmission slots. Any changes toallocation patterns based on the negotiations 118 may be provided to theRAN 102 via a self-optimizing network (SON) 122.

In various implementations, RAN 102 may be one of a number of accessnetworks of a telecommunications service provider. Thetelecommunications service provider may operate a telecommunicationsnetwork that includes access networks, such as RAN 102, a core network,such as core network 116, and a management plane, such as SON 122. Thetelecommunications service provider may have licenses to bands of radiofrequency spectrum and the RANs may provide wireless coverage viadifferent parts of the licensed frequency bands. The coverage providedby each RAN may vary based on the technology of that RAN. For example, aFourth Generation (4G) RAN may provide access via one set of frequencybands and a Fifth Generation (5G) RAN may provide access via a differentor overlapping set of frequency bands.

RANs of the telecommunications network, such as RAN 102, may utilize anyThird Generation Partnership Project (3GPP) Standard Third Generation(3G), 4G, 5G, etc. technology or other 3G, 4G, 5G, etc. technology.Alternatively or additionally, example RANs, such as RAN 102, mayutilize unlicensed wireless networks, such as WiFi® or WiMax® networks,and/or wired access networks.

As illustrated in FIG. 1 , the RAN 102 may include a cell tower; one ormore base station units coupled to the cell tower, offering connectivityto cell 104, and using one or more technology types; one or more powersources; and mechanisms for connecting the base station unit(s) to thecore network 116. For example, the RAN 102 may include an eNode B (eNB)base station for supporting an LTE connection, a gNode B (gNB) basestation for supporting a NR connection, or both. The eNB and gNB may beimplemented in a single computing device or through multiple computingdevices and may represent an ENDC (E-UTRAN (Evolved UMTS (UniversalMobile Telecommunications Service) Terrestrial Radio Access Network) NewRadio—Dual Connectivity) solution. The ENDC solution enables the UEs 106to connect to the eNB through an LTE connection, with the eNB serving asa master node, and to the gNB through a NR connection, with the gNBserving as a secondary node. ENDC solutions are specified in greaterdetail by 3GPP standards.

RAN 102 may also include a scheduler to allocate time slots forfrequency bands, as well as downlink buffers, a configuration module,and an internetwork module. An example computing device configured toimplement the RAN 102 is illustrated in FIG. 4 and described furtherherein with reference to that figure.

In some implementations, cell 104 may correspond to a single geographicarea in which the RAN 102 provides coverage. In other implementations,cell 104 may correspond to multiple, overlapping geographic area inwhich multiple base stations of RAN 102 provide coverage.

UEs 106, including UE 106 a and UE 106 b, are located within cell 104;FIG. 1 shows UE 106 a and UE 106 b at different locations within cell104. In various implementations, each UE 106 may be any sort of wirelesscommunication device, such as a cellular handset, a tablet computer, apersonal computer, a desktop computing device, a media player, etc. EachUE 106 may include one or more radios for wireless communication and/orwired port(s), may include both input and output components, and mayhave a Subscriber Identity Module (SIM) or other technology thatsecurely stores identity information for the UE 106. Further, each UE106 may include a radio protocol stack, applications, and locationsensors. An example UE 106 is illustrated in FIG. 5 and describedfurther herein with reference to that figure.

In some implementations, each of UE 106 a and UE 106 b have uplinkcommunications, downlink communications, or both to engage in. Suchcommunications may be connected to applications of the UEs 106 or totheir platforms. For example, communications may include voice calling,video calling, text messaging, multimedia messaging, conferencing,streaming media, browsing of network content, participation in socialmedia, participation in online games, etc. Different ones of thesecommunications may require more downlink bandwidth or more uplinkbandwidth. Also, different locations in the cell 104 may be associatedwith greater needs for downlink or uplink due to characteristics of theassociated cellular technology or due to geographic features (hills,buildings, etc.).

Upon any change in conditions—such as location of the UE 106, change inthe application executing on the UE 106, or change in RAN conditions,such as signal strength, signal quality, packet loss, or RAN load, theUE 106 may provide indicia to the RAN 102. Such indicia may representonly values that have changed or may represent a list of valuesdetermined by a configuration of the UE 106. Responsive to determining achange in any of the conditions mentioned above (or other conditions), aPacket Data Control Protocol (PDCP) layer of the radio protocol stack ofthe UE 106 may measure or otherwise determine the values to include inthe indicia. The indicia may then be provided to the RAN 102 via theRadio Link Control (RLC) layer of the radio protocol stack. Such indiciamay include RAN conditions signal strength, signal quality, packet loss,or RAN load, or other information about the UE 106, such as location,active applications, etc. In some implementations, the location may bedetermined by a location sensor of the UE 106. Additionally, the indiciamay include desired allocations of uplink or downlink, these beingspecified by applications or by the radio protocol stack. FIG. 1illustrates two examples of indicia: indicia 108, transmitted to the RAN102 by UE 106 a, and indicia 112 transmitted to the RAN 102 by 106 b. Asshown, each of indicia 108 and 112 may reflect different locations anddifferent RAN conditions.

Upon receiving indicia from any UE 106, the scheduler of the RAN 102 maydetermine an allocation of uplink transmission slots and downlinktransmission slots for that UE 106. In determining allocations, thescheduler considers a number of factors. For example, the schedulerlooks at RAN conditions and UE information in the received indicia andin indicia received from other UEs 106 within the cell 104 (e.g.,indicia received within some previous time period). In one example, thescheduler may note that two UEs 106 are each streaming video, but thatone UE 106 is at the cell edge while the other is close to the celltower. Given these different locations and the applications used, thescheduler may assign a greater proportion of downlink slots to both, butif availability of downlink is limited, the scheduler may give a greaterratio of downlink slots to the UE 106 at the cell edge.

The scheduler may also consider both outer boundary ratios and downlinkbuffers when allocating transmission slots. For example, downlink may bebounded at ninety percent of total slots. So for every ten slots, nomore than nine may be download. A similar boundary ratio may apply foruplink. Even when the indicia would lead the scheduler to heavily weighassignment of transmission slots to one of downlink or uplink, theboundary ratios limit its ability to do so.

In various implementations, the scheduler of the RAN 102 may also beconstrained by configuration received by SON 122 and/or by requirementsto obtain approval from the telecommunications network. Such approvalmay be handled by an internetworking module of the RAN 102, which mayobtain a proposed allocation of uplink transmission slots and downlinktransmission slots from the scheduler, provide the proposed allocationsto a telecommunications network service implemented, e.g., in the corenetwork 116 of the telecommunications network, and obtain approval ordisapproval in response. Alternatively, the internetworking module maycontact adjacent cells of other telecommunication networks 120 via theX2 interface to exchange proposed allocations. The result of theexchange may then be evaluated based on a configuration received fromthe SON 122.

Whether constrained by configuration or by direct approval from atelecommunications network service, the constraints may reflectnegotiation 118 between telecommunications network providers. Devices ofthe core network 116 and other telecommunications network 120 maypropagate results of the negotiations 118. For example, results of thenegotiations 118 may be provided to SON 122 and used to update aconfiguration for the RAN 102. Additionally or alternatively, results ofthe negotiations 118 may be used to respond to requests for approval ofallocations from RANs, such as RAN 102.

The telecommunications network providers may determine times at whichgreater downlink or uplink allocations may be made at differentfrequency bands and at different locations. They may also definecircumstances in which RANs are to fall back to making defaultallocations (e.g., 3 downlink slots to every 1 uplink slot) or tofollowing a set of allocation patterns at different times, in differentlocations, or under different conditions. The results of thesenegotiations 118, including defaults and patterns, are then used asconfigurations and/or approval criteria in the manner described above.

In various implementations, the SON 122 may be a management plane forreceiving performance information from RANs and updating configurationsof those RANs in response. In the context of FIG. 1 , the SON 122 mayreceive some or all of the information provided in indicia 108 and 112,as well as other information tracked by the RAN 102 (e.g., downlinkbuffer sizes), and, in some examples, configuration information relatedto negotiations 118. Based on such received information, the SON 122 maygenerate an updated configuration for RAN 102 and provide the updatedconfiguration to RAN 102 via the configuration module of the RAN 102.

After the scheduler of the RAN 102 has taken into account receivedinformation, configuration, and any needed approvals, the allocation 110for UE 106 a and allocation 114 for UE 106 b may be provided to thoseUEs 106. As shown in FIG. 1 , the allocation 110 may differ fromallocation 114, whether because of different transmission needs orbecause of limitations or constraints on either uplink or downlink. EachUE 106 may then utilize the allocated slots in transmitting andreceiving communications, as described above.

In some implementations, as noted above, a UE 106 may repeat thedetermining and providing of indicia and receiving of allocations oftransmission slots in response to moving to another location or activelyusing a different application. These movements or use changes may resultin different indicia and, possibly, different allocations. In variousimplementations, however, the changes may lead to different indicia butnot to different allocations. For example, when the RAN 102 is using adefault allocation or allocation pattern, changes in the factorsmeasured by the indicia may not lead to changes in allocation. Rather,indicia may not effect allocations, or may only effect a choice betweena small, limited set of options. In such examples, RAN 102 may configurethe UE 106 to either suspend providing of indicia or to provide asmaller subset.

Example Operations

FIGS. 2-3 illustrate example processes. These processes are illustratedas logical flow graphs, each operation of which represents a sequence ofoperations that can be implemented in hardware, software, or acombination thereof. In the context of software, the operationsrepresent computer-executable instructions stored on one or morecomputer-readable storage media that, when executed by one or moreprocessors, perform the recited operations. Generally,computer-executable instructions include routines, programs, objects,components, data structures, and the like that perform particularfunctions or implement particular abstract data types. The order inwhich the operations are described is not intended to be construed as alimitation, and any number of the described operations can be combinedin any order and/or in parallel to implement the processes.

FIG. 2 illustrates a flow chart of an example process for receivingindicia from UEs, determining allocations of transmission slots to UEs,and providing those allocations. As illustrated at 202, a RAN device mayreceive indicia about RAN conditions or about UEs in a vicinity of theRAN. In some implementations, the RAN conditions may include at leastone of signal strength, signal quality, packet loss, or RAN load and theindicia about the UEs in the vicinity of the RAN may include locationsof the UEs, applications active on the UEs, or a desired allocationratio of uplink transmission slots to downlink transmission slots.

At 204, the RAN device may provide one or more network measurements orUE measurements to a SON and, at 206, may receive, from the SON, anupdated configuration to be utilized by the RAN device in determiningallocations of transmission slots. Though illustrated between theoperations shown at 202 and at 208, operations 204-206 may occur at anypoint in the process(es) illustrated in FIG. 2 .

At 208, the RAN device may then determine, based at least in part on theindicia, a first allocation of uplink and downlink transmission slots toa first UE and a second allocation of uplink and downlink transmissionslots to a second UE. In some implementations, the first allocation maydiffer from the second allocation. At 210, the determining may includedetermining the first allocation and the second allocation based atleast in part on outer boundary ratios for allocation of uplinktransmission slots and downlink transmission slots. At 212, thedetermining may further be based at least in part on downlink buffer(s)associated with the UE. Also, in some implementations, the first UE andthe second UE may be engaged in similar activities but may be atdifferent relative locations within a cell associated with the RAN.

At 214, the RAN device may then communicate with a device of anothertelecommunication network via an X2 interface, providing, at 216, thefirst allocation and the second allocation and a spectrum identificationto a telecommunication network service. At 218, the RAN device thenreceives, in response, approval or disapproval of the first allocationand the second allocation.

If receiving approval, the RAN device may then provide, at 220, thefirst allocation to the first UE and the second allocation to the secondUE. If, on the other hand, disapproval is received, the RAN device mayinstead provide, at 222, a default allocation to the first UE and thesecond UE. In some implementations, the default allocation may be basedat least in part on the first allocation, the second allocation, andallocation(s) provided by other RANs.

FIG. 3 illustrates a flow chart of an example process for providingindicia to a RAN and receiving in return an allocation of transmissionslots. As illustrated, at 302, a UE may send a first request for a firstallocation of uplink transmission slots and downlink transmission slotsfrom a RAN. The request may include indicia about RAN conditions orabout the UE. For example, the RAN conditions may include at least oneof signal strength, signal quality, packet loss, or RAN load and theindicia about the UE may include a location of the UE, an applicationactive on the UE, or a desired allocation ratio of uplink transmissionslots to downlink transmission slots. In some implementations, theindicia are determined at a PDCP layer of the UE and communicated by aRLC layer of the UE. At 304, the UE may then receive, in return, thefirst allocation of uplink transmission slots and downlink transmissionslots.

At 306, the UE may determine that a location of the UE has changed orthat an application active on the UE has changed. Responsive to thedetermining, the UE may send, at 308, a second request for a secondallocation of uplink transmission slots and downlink transmission slotsfrom the RAN. At 310, the UE may then receive, from the RAN, the secondallocation of uplink transmission slots and downlink transmission slots.In various implementations, the first allocation of uplink transmissionslots and downlink transmission slots may differ from the secondallocation of uplink transmission slots and downlink transmission slots.

At 312, the UE may determine a second time that the location of the UEhas changed or that the application active on the UE has changed.Responsive to the determining, the UE may send, at 314, a third requestfor a third allocation of uplink transmission slots and downlinktransmission slots from the RAN. At 316, the UE may then receive, fromthe RAN, the third allocation of uplink transmission slots and downlinktransmission slots. In various implementations, third allocation ofuplink transmission slots and downlink transmission slots may be thesame as the second allocation of uplink transmission slots and downlinktransmission slots.

Example Architectures

FIG. 4 illustrates an example architecture of a computing device of aRAN configured to receive indicia from a UE and to provide, in return,an allocation of transmission slots to the UE. The RAN may be an exampleof a RAN 102, which is described further herein. The RAN device 400 canhave a system memory 402. The system memory 402 can store a scheduler404, a configuration module 406, an internetworking module 408, downlinkbuffers 410, and/or other modules and data 412. The computing device 400can also include processor(s) 414, removable storage 416, non-removablestorage 418, input device(s) 420, output device(s) 422, andtransceiver(s) 424.

In various examples, system memory 402 can be volatile (such asrandom-access memory (RAM)), non-volatile (such as read-only memory(ROM), flash memory, etc.), or some combination of the two. Examplesystem memory 402 can include one or more of RAM, ROM, electronicallyerasable programmable ROM (EEPROM), a Flash Memory, a hard drive, amemory card, an optical storage, a magnetic cassette, a magnetic tape, amagnetic disk storage or another magnetic storage devices, or any othermedium.

Examples of the scheduler 404, configuration module 406, internetworkingmodule 408, and downlink buffers 410 are described above in detail withreference to FIG. 1 .

The other modules and data 412 can be utilized by the computing device400 to perform or enable performing any action taken by the computingdevice 400. The other modules and data 412 can include a platform andapplications, and data utilized by the platform and applications.

In some embodiments, the processor(s) 414 can be a central processingunit (CPU), a graphics processing unit (GPU), both CPU and GPU, or otherprocessing unit or component known in the art.

The computing device 400 can also include additional data storagedevices (removable and/or non-removable) such as, for example, magneticdisks, optical disks, or tape. Such additional storage is illustrated inFIG. 4 by removable storage 416 and non-removable storage 418.Non-transitory computer-readable media may include volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information, such as computer readableinstructions, data structures, program modules, or other data. Systemmemory 402, removable storage 416 and non-removable storage 418 are allexamples of non-transitory computer-readable media. Non-transitorycomputer-readable media include, but are not limited to, RAM, ROM,EEPROM, flash memory or other memory technology, compact disc-ROM(CD-ROM), digital versatile discs (DVD) or other optical storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or any other medium which can be used to storethe desired information and which can be accessed by the computingdevice 400. Any such computer-readable storage media can be part of thecomputing device 400. In various examples, any or all of system memory402, removable storage 416, and non-removable storage 418, storeprogramming instructions which, when executed, implement some or all ofthe above-described operations of the computing device 400.

In some examples, the computing device 400 can also have input device(s)420, such as a keyboard, a mouse, a touch-sensitive display, voice inputdevice, etc., and/or output device(s) 422 such as a display, speakers, aprinter, etc. These devices are well known in the art and need not bediscussed at length here.

The computing device 400 can also include one or more transceivers, suchas a New Radio (NR) transceiver or a Long-Term Evolution (LTE)transceiver to facilitate communication with other devices, such as oneor more UEs 106.

FIG. 5 illustrates an example architecture of a computing device of a UEconfigured to provide indicia to a RAN and to receive, in return, anallocation of transmission slots. The UE 500 may be an example of a UE106, which is described further herein. The UE 500 can have a systemmemory 502. The system memory 502 can store a radio protocol stack 504,application(s) 506, location sensor(s) 508, and/or other modules anddata 510. The UE 500 can also include processor(s) 512, removablestorage 514, non-removable storage 516, input device(s) 518, outputdevice(s) 520, and transceiver(s) 522.

In various examples, system memory 502 can be volatile (such asrandom-access memory (RAM)), non-volatile (such as read-only memory(ROM), flash memory, etc.), or some combination of the two. Examplesystem memory 502 can include one or more of RAM, ROM, electronicallyerasable programmable ROM (EEPROM), a Flash Memory, a hard drive, amemory card, an optical storage, a magnetic cassette, a magnetic tape, amagnetic disk storage or another magnetic storage devices, or any othermedium.

Examples of the radio protocol stack 504, application(s) 506, andlocation sensor(s) 508 are described above in detail with reference toFIG. 1 .

The other modules and data 510 can be utilized by the computing device500 to perform or enable performing any action taken by the computingdevice 500. The other modules and data 510 can include a platform andapplications, and data utilized by the platform and applications.

In some embodiments, the processor(s) 512 can be a central processingunit (CPU), a graphics processing unit (GPU), both CPU and GPU, or otherprocessing unit or component known in the art.

The UE 500 can also include additional data storage devices (removableand/or non-removable) such as, for example, magnetic disks, opticaldisks, or tape. Such additional storage is illustrated in FIG. 5 byremovable storage 514 and non-removable storage 516. Non-transitorycomputer-readable media may include volatile and nonvolatile, removableand non-removable media implemented in any method or technology forstorage of information, such as computer readable instructions, datastructures, program modules, or other data. System memory 502, removablestorage 514 and non-removable storage 516 are all examples ofnon-transitory computer-readable media. Non-transitory computer-readablemedia include, but are not limited to, RAM, ROM, EEPROM, flash memory orother memory technology, compact disc-ROM (CD-ROM), digital versatilediscs (DVD) or other optical storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by the UE 500. Any such computer-readable storage media canbe part of the UE 500. In various examples, any or all of system memory502, removable storage 514, and non-removable storage 516, storeprogramming instructions which, when executed, implement some or all ofthe above-described operations of the UE 500.

In some examples, the UE 500 can also have input device(s) 518, such asa touch-sensitive display, voice input device, etc., and/or outputdevice(s) 520 such as a display, speakers, etc. These devices are wellknown in the art and need not be discussed at length here.

The UE 500 can also include one or more transceivers 522, such as an NRtransceiver or an LTE transceiver to facilitate communication with otherdevices, such as a RAN 102.

CONCLUSION

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter is not necessarily limited to the specificfeatures or acts described above. Rather, the specific features and actsdescribed above are disclosed as example embodiments.

What is claimed is:
 1. A method comprising: receiving, by a radio areanetwork (RAN) device associated with a RAN, indicia about RAN conditionsor about user equipment (UE) in a vicinity of the RAN; determining, bythe RAN device, based at least in part on the indicia, a firstallocation of uplink and downlink transmission slots to a first UE and asecond allocation of uplink and downlink transmission slots to a secondUE, wherein the first allocation differs from the second allocation;providing one or more network measurements or UE measurements to aSelf-Optimizing Network (SON); receiving, from the SON, an updatedconfiguration to be utilized by the RAN device in determining the firstallocation and the second allocation; and providing, by the RAN device,the first allocation to the first UE and the second allocation to thesecond UE.
 2. The method of claim 1, further comprising instead ofproviding the first allocation to the first UE and the second allocationto the second UE, providing a default allocation to the first UE and thesecond UE.
 3. The method of claim 2, wherein the default allocation isbased at least in part on the first allocation, the second allocation,and allocations provided by other RANs.
 4. The method of claim 1,wherein the RAN conditions include at least one of signal strength,signal quality, packet loss, or RAN load and the indicia about the UE inthe vicinity of the RAN includes locations of the UE, applicationsactive on the UE, or a desired allocation ratio of uplink transmissionslots to downlink transmission slots.
 5. The method of claim 1, whereindetermining the first allocation and the second allocation is furtherbased at least in part on downlink buffers associated with the UE. 6.The method of claim 1, wherein the first UE and the second UE areengaged in similar activities but are at different relative locationswithin a cell associated with the RAN.
 7. The method of claim 1, furthercomprising communicating with a device of another telecommunicationnetwork via an X2 interface.
 8. A Radio Access Network (RAN) comprising:a processor; a transceiver coupled to the processor; and a schedulerexecuted by the processor to perform operations including: receivingindicia about RAN conditions or about user equipment (UE) in a vicinityof the RAN; determining based at least in part on the indicia, a firstallocation of uplink and downlink transmission slots to a first UE and asecond allocation of uplink and downlink transmission slots to a secondUE, wherein the first allocation differs from the second allocation anddetermining the first allocation and the second allocation is based atleast in part on downlink buffers associated with the UE; and providingthe first allocation to the first UE and the second allocation to thesecond UE.
 9. The RAN of claim 8, further comprising: providing one ormore network measurements or UE measurements to a Self-OptimizingNetwork (SON); and receiving, from the SON, an updated configuration tobe utilized by a RAN device in determining the first allocation and thesecond allocation.
 10. The RAN of claim 8, wherein the operationsfurther include instead of providing the first allocation to the firstUE and the second allocation to the second UE, providing a defaultallocation to the first UE and the second UE.
 11. The RAN of claim 10,wherein the default allocation is based at least in part on the firstallocation, the second allocation, and allocations provided by otherRANs.
 12. The RAN of claim 8, wherein the RAN conditions include atleast one of signal strength, signal quality, packet loss, or RAN loadand the indicia about the UE in the vicinity of the RAN includeslocations of the UE, applications active on the UE, or a desiredallocation ratio of uplink transmission slots to downlink transmissionslots.
 13. A non-transitory computer-readable medium having storedthereon executable instructions for programming a user equipment (UE) toperform operations comprising: sending a first request for a firstallocation of uplink transmission slots and downlink transmission slotsfrom a radio access network (RAN); receiving, from the RAN, the firstallocation of uplink transmission slots and downlink transmission slots;determining that a location of the UE has changed or that an applicationactive on the UE has changed; responsive to the determining, sending asecond request for a second allocation of uplink transmission slots anddownlink transmission slots from the RAN; receiving, from the RAN, thesecond allocation of uplink transmission slots and downlink transmissionslots; and receiving, from the RAN, a default allocation, the defaultallocation being based at least in part on the first allocation and thesecond allocation.
 14. The non-transitory computer-readable medium ofclaim 13, wherein the first allocation of uplink transmission slots anddownlink transmission slots differs from the second allocation of uplinktransmission slots and downlink transmission slots.
 15. Thenon-transitory computer-readable medium of claim 13, wherein the requestincluding indicia about RAN conditions or about the UE.
 16. Thenon-transitory computer-readable medium of claim 15, wherein the indiciaare determined at a packet data control protocol (PDCP) layer of the UEand communicated by a radio link control (RLC) layer of the UE.
 17. Thenon-transitory computer-readable medium of claim 15, wherein the RANconditions include at least one of signal strength, signal quality,packet loss, or RAN load and the indicia about the UE include a locationof the UE, an application active on the UE, or a desired allocationratio of uplink transmission slots to downlink transmission slots. 18.The non-transitory computer-readable medium of claim 13, wherein theoperations further comprise: determining a second time that the locationof the UE has changed or that the application active on the UE haschanged; responsive to determining the second time, sending a thirdrequest for a third allocation of uplink transmission slots and downlinktransmission slots from the RAN; and receiving, from the RAN, the thirdallocation of uplink transmission slots and downlink transmission slots,wherein the third allocation of uplink transmission slots and downlinktransmission slots is the same as the second allocation of uplinktransmission slots and downlink transmission slots.
 19. Thenon-transitory computer-readable medium of claim 13, wherein the defaultallocation is further determined based at least in part on allocationsprovided by other RANs.
 20. The non-transitory computer-readable mediumof claim 13, wherein the operations further comprise providing one ormore UE measurements to at least one of the RAN or a Self-OptimizingNetwork (SON).